-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fixing bug in labeler #15406
fixing bug in labeler #15406
Conversation
I see you updated files related to
|
@@ -1263,7 +1263,7 @@ func NewEngine(ctx context.Context, cfg Config) (engine *Engine, err error) { | |||
engine = &Engine{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note @cedric-cordenier @justinkaseman that this hex encoded value from workflow.name = hex.EncodeToString([]byte(cfg.WorkflowName))
is passed into the engine, which has downstream consumers like
chainlink/core/services/workflows/engine.go
Line 442 in 7dcc1fd
WorkflowName: e.workflow.name, |
Do capabilities expect a hex encoded string for workflow name? (maybe you expected long workflow names?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, consumers expect hex encoded strings.
@@ -1263,7 +1263,7 @@ func NewEngine(ctx context.Context, cfg Config) (engine *Engine, err error) { | |||
engine = &Engine{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, consumers expect hex encoded strings.
AER Report: CI Core ran successfully ✅ |
https://github.com/smartcontractkit/chainlink/blame/develop/core/services/workflows/engine.go#L1261 uses a hex encoded version of the workflow name string instead of the workflow name string itself.